docs(solid-query): correct devtools development-mode explanation - #11409
docs(solid-query): correct devtools development-mode explanation#11409grzdev wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe Solid Query Devtools documentation now states that devtools use ChangesSolid Devtools Documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The Solid Query Devtools documentation now accurately describes its development-only, client-only behavior without changing runtime code or published artifacts. The change is ready to merge. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🎯 Changes
The devtools documentation incorrectly describes
isServer === trueas the condition for including devtools.Update it to reflect the implementation:
isDevenables the devtools in development, the components render nothing in production, and loading happens only on the client.Documentation only. Verified against the entry point and client-only wrapper;
git diff --checkpasses.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit